Triple
T31747743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G01 |
E810317
|
entity |
| Predicate | numberInZone |
P165501
|
FINISHED |
| Object | 01 |
—
|
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: 01 | Statement: [G01, numberInZone, 01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInZone Context triple: [G01, numberInZone, 01]
-
A.
zoneNumbering
Indicates a relationship where specific zones are assigned or associated with particular identifying numbers.
-
B.
zoneNumberInGame
chosen
Indicates that an entity is associated with a specific numbered zone within a game.
-
C.
zoneNumberRange
Indicates that there is an associated range of zone numbers, typically specifying the minimum and maximum zone identifiers applicable in a given context.
-
D.
numberOfZones
Indicates the quantity of distinct zones associated with or contained by a given entity.
-
E.
railwayZoneNumber
Indicates the specific numbered zone of a railway network within which the referenced entity is located or classified.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a013d7180d08190b76f64cb430af9e1 |
completed | May 11, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_6a013c77d23c8190bb59e458b506d6e9 |
completed | May 11, 2026, 2:18 a.m. |
Created at: April 30, 2026, 11:27 p.m.