Triple
T4598376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weldon Spring Ordnance Works |
E100258
|
entity |
| Predicate | hasReuse |
P29363
|
FINISHED |
| Object | interpretive center |
—
|
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: interpretive center | Statement: [Weldon Spring Ordnance Works, hasReuse, interpretive center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReuse Context triple: [Weldon Spring Ordnance Works, hasReuse, interpretive center]
-
A.
hasFormerUse
chosen
Indicates that something previously served a particular function or role that it no longer has.
-
B.
keyReuse
Indicates that the same key is used multiple times, rather than being uniquely generated or dedicated for a single use or context.
-
C.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
D.
usesRepetition
Indicates that one entity employs repeated elements, actions, or patterns as a deliberate feature or technique in relation to another entity or context.
-
E.
hasAdjacentUse
Indicates that one entity is used or occurs directly next to another in space, time, or sequence.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59707f8c8190b8368f1de887ff2a |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.