Triple
T7395073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Co3 |
E170600
|
entity |
| Predicate | hasPermutationRank |
P76340
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Co3, hasPermutationRank, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPermutationRank Context triple: [Co3, hasPermutationRank, 3]
-
A.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
B.
hasComparableRank
Indicates that two entities hold positions or levels that are equivalent or similar in rank within a given hierarchy or system.
-
C.
hasRankVariant
Indicates that one entity is an alternative or variant form of another entity’s rank or hierarchical level.
-
D.
isRankedAbove
Indicates that one entity holds a higher position or status in an ordered ranking than another entity.
-
E.
hasRankingAlgorithm
Indicates that an entity uses or is associated with a specific algorithm for ranking or ordering items.
- F. None of above. chosen
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_69c68a5f04188190ac266569c9280347 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2279de4819081b8876d02f55388 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0be2b1c8190bea06100a7caef2b |
completed | March 27, 2026, 9:03 p.m. |
Created at: March 27, 2026, 3:09 p.m.