Triple
T27598898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T. |
E699980
|
entity |
| Predicate | associatedWithPersonRank |
P167075
|
FINISHED |
| Object | General |
—
|
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: General | Statement: [T., associatedWithPersonRank, General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPersonRank Context triple: [T., associatedWithPersonRank, General]
-
A.
associatedWithRank
Indicates a relationship where an entity is linked to a specific rank, level, or hierarchical position.
-
B.
hasHighRankAssociatedWith
Indicates that one entity is associated with another entity that holds a high rank, status, or level within a given hierarchy or system.
-
C.
hasRankedPerson
chosen
Indicates that an entity has assigned or holds a person in a specific rank or ordered position relative to others.
-
D.
namedPersonAssociation
Indicates a relationship where one entity is associated with or identified by a specific personal name.
-
E.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a00233e2170819084bee0c8f74cc1a4 |
completed | May 10, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_6a0022943fd08190b73007f080d5971d |
completed | May 10, 2026, 6:15 a.m. |
Created at: April 27, 2026, 2:07 p.m.