Triple
T37755560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fabricius |
E941100
|
entity |
| Predicate | relatedModernSurname |
P34736
|
FINISHED |
| Object | Fabricius (modern surname) |
E941100
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Fabricius (modern surname) | Statement: [Fabricius, relatedModernSurname, Fabricius (modern surname)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedModernSurname Context triple: [Fabricius, relatedModernSurname, Fabricius (modern surname)]
-
A.
hasModernNamesake
chosen
Indicates that an entity is the namesake or inspiration for a modern entity that shares or derives its name from it.
-
B.
isModernName
Indicates that a given name is considered modern or contemporary in usage or origin, as opposed to traditional or historical.
-
C.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
D.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
E.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40e07d5e248190bd44225f849b2a43 |
completed | June 28, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.