Triple
T3532908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crossroads of the Marine Corps |
E74701
|
entity |
| Predicate | appliedToSince |
P26568
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Crossroads of the Marine Corps, appliedToSince, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToSince Context triple: [Crossroads of the Marine Corps, appliedToSince, 20th century]
-
A.
appliedSince
chosen
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
B.
basedAtSince
Indicates that an entity has been continuously based or located at a specific place starting from a given point in time.
-
C.
observedSince
Indicates that one entity has been continuously or repeatedly observed starting from a specified point in time.
-
D.
representedSince
Indicates that one entity has been acting as a representative or agent for another entity continuously from a specified starting time.
-
E.
areUsedSince
Indicates that entities have been in use continuously starting from a specified point in time.
- 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_69ad85d1a3948190931fd1ea1f49717b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc9b945481909867d44b810e8b1f |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae13ab808190a5d6ecdc7543445e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.