Triple
T24383544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine-class armored cruiser |
E614677
|
entity |
| Predicate | precededByConcept |
P50919
|
FINISHED |
| Object | traditional armored cruiser |
—
|
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: traditional armored cruiser | Statement: [Maine-class armored cruiser, precededByConcept, traditional armored cruiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByConcept Context triple: [Maine-class armored cruiser, precededByConcept, traditional armored cruiser]
-
A.
predecessorInConcept
chosen
Indicates that one concept temporally or logically comes before another in a sequence or developmental progression.
-
B.
classPrecededBy
Indicates that one class occurs or is scheduled before another class in a sequence or timetable.
-
C.
precededByUse
Indicates that one use, action, or event occurs earlier in time and is directly followed by another specified use, action, or event.
-
D.
precededByDocument
Indicates that one document occurs or is issued earlier in sequence or time than another document.
-
E.
precededByPractice
Indicates that an event, state, or action occurs only after and is directly preceded by a period of practice.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f294533b3881908c228a021c254006 |
completed | April 29, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f287c4a2b48190b80fb7a3c0e9b018 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:03 a.m.