Triple
T3804677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracy |
E91775
|
entity |
| Predicate | becameCommonAsGivenNameIn |
P19169
|
FINISHED |
| Object | 20th century |
—
|
LITERAL 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: 20th century | Statement: [Tracy, becameCommonAsGivenNameIn, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameCommonAsGivenNameIn Context triple: [Tracy, becameCommonAsGivenNameIn, 20th century]
-
A.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
B.
givenNameFor
Indicates that one entity is the personal first name assigned to or used for another entity.
-
C.
isCommonAsFirstName
chosen
Indicates that the referenced name is frequently used as a first (given) name within a specified population or context.
-
D.
formerName
Indicates that an entity was previously known by a different name in the past.
-
E.
commonNameOf
Indicates that one entity is the commonly used or popular name by which the other entity is known.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.