Triple
T18569092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICC Test Team Rankings |
E453830
|
entity |
| Predicate | outputField |
P77812
|
FINISHED |
| Object | team name |
—
|
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: team name | Statement: [ICC Test Team Rankings, outputField, team name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputField Context triple: [ICC Test Team Rankings, outputField, team name]
-
A.
outputProperty
chosen
Indicates that a property or attribute is produced, exposed, or yielded as the output of a process, function, or system.
-
B.
outputOf
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
C.
outputSpecifier
Indicates how the result or outcome of an action, process, or computation is to be formatted, structured, or delivered.
-
D.
outputsTo
Indicates that the result or data produced by one entity is directed or sent to another entity as its destination or target.
-
E.
outputFunction
Indicates that one entity serves as the function or procedure responsible for producing or returning the output of another entity or process.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b0075a08190a5d590d36089ca1e |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.