Triple
T31157087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitz |
E794238
|
entity |
| Predicate | isPrefixIn |
P66954
|
FINISHED |
| Object | Fitzgerald |
—
|
NE NERFINISHED |
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: Fitzgerald | Statement: [Fitz, isPrefixIn, Fitzgerald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrefixIn Context triple: [Fitz, isPrefixIn, Fitzgerald]
-
A.
hasPrefix
chosen
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
B.
usedAsPrefixIn
Indicates that one element functions as a leading prefix component in the formation or representation of another element.
-
C.
hasPrepositionalPrefix
Indicates that one entity functions as a prepositional prefix attached to or modifying another entity.
-
D.
isSubsequenceOf
Indicates that one sequence can be derived from another by deleting zero or more elements without changing the order of the remaining elements.
-
E.
hasPrefixMeaning
Indicates that one entity serves as a semantic prefix of another, contributing a specific meaning to the start of the second entity.
- F. None of above.
Provenance (3 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:07 p.m.