Triple
T10301553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NM-79 |
E241642
|
entity |
| Predicate | operatedUnderground |
P92992
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NM-79, operatedUnderground, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUnderground Context triple: [NM-79, operatedUnderground, true]
-
A.
isUndergroundOnly
Indicates that something exists, operates, or is accessible exclusively below ground level and not above ground.
-
B.
operatedAsUndergroundMovementUntil
Indicates that an organization or group functioned covertly as an underground movement up to a specified point in time.
-
C.
hasUndergroundSection
Indicates that an entity includes a portion or segment that is located below ground level.
-
D.
openedAsUndergroundStation
Indicates that an entity began operation specifically as an underground railway/metro station at the time it was opened.
-
E.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d30716d8819085e25a78e6af3b9d |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d29d7cf08190acd70cee634c5cdb |
completed | April 7, 2026, 9:47 a.m. |
Created at: April 6, 2026, 11:44 a.m.