Triple
T866386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortune 500 |
E18711
|
entity |
| Predicate | subjectOfRanking |
P4846
|
FINISHED |
| Object | largest U.S. companies by revenue |
—
|
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: largest U.S. companies by revenue | Statement: [Fortune 500, subjectOfRanking, largest U.S. companies by revenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfRanking Context triple: [Fortune 500, subjectOfRanking, largest U.S. companies by revenue]
-
A.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
B.
selectionRankingEndPoint
Indicates the position or boundary in an ordered list at which a selection or ranking process concludes.
-
C.
rankedBy
chosen
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
D.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
E.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7cb1888190a46c16b30256451b |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.