Triple
T11893908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 3–Red |
E282987
|
entity |
| Predicate | hasSystemType |
P71779
|
FINISHED |
| Object | metro |
—
|
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: metro | Statement: [Line 3–Red, hasSystemType, metro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSystemType Context triple: [Line 3–Red, hasSystemType, metro]
-
A.
belongsToSystemType
chosen
Indicates that one entity is classified under, or is a member of, a particular system type.
-
B.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
E.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd1172988190a2c13d37220f2f93 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.