Triple
T3741848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLVS |
E79718
|
entity |
| Predicate | hasLocationCode |
P1289
|
FINISHED |
| Object | VS |
—
|
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: VS | Statement: [CLVS, hasLocationCode, VS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationCode Context triple: [CLVS, hasLocationCode, VS]
-
A.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
B.
hasStationCode
chosen
Indicates that an entity is associated with a specific station identification code.
-
C.
hasBuildingLocation
Indicates that a building is situated at, or associated with, a specific geographic or spatial location.
-
D.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
-
E.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb549490819084ebe69aae5ccf95 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.