Triple
T1475694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camden Yards station |
E30834
|
entity |
| Predicate | openingPurpose |
P25761
|
FINISHED |
| Object | serve Camden Yards sports complex |
—
|
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: serve Camden Yards sports complex | Statement: [Camden Yards station, openingPurpose, serve Camden Yards sports complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingPurpose Context triple: [Camden Yards station, openingPurpose, serve Camden Yards sports complex]
-
A.
openingMotive
chosen
Indicates the initial reason, trigger, or intent that prompts an action or event to begin.
-
B.
openingAnswer
Indicates that an entity provides an initial or first response in a dialogue, interaction, or sequence of answers.
-
C.
opens
Indicates that one entity causes or allows another entity (such as an object, space, or resource) to become accessible or no longer closed.
-
D.
openingVerb
Indicates that an entity performs the initial or primary action that begins an event, process, or interaction.
-
E.
openingInvocation
Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c602387c8190b97a20c8e05e3d16 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.