Triple
T32185798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PO2 |
E822104
|
entity |
| Predicate | hasRankCode |
P48323
|
FINISHED |
| Object | PO2 |
—
|
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: PO2 | Statement: [PO2, hasRankCode, PO2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankCode Context triple: [PO2, hasRankCode, PO2]
-
A.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
B.
hasRankNumber
Indicates that an entity is assigned a specific ordinal or hierarchical position represented by a numerical rank.
-
C.
rankCode
chosen
Indicates the specific rank or hierarchical level assigned to an entity, typically encoded as a standardized code.
-
D.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
E.
hasRanks
Indicates that one entity possesses, is assigned, or is associated with one or more rank levels or hierarchical positions.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 12:35 a.m.