Triple
T24383545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine-class armored cruiser |
E614677
|
entity |
| Predicate | followedByConcept |
P111872
|
FINISHED |
| Object | early battleship |
—
|
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: early battleship | Statement: [Maine-class armored cruiser, followedByConcept, early battleship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedByConcept Context triple: [Maine-class armored cruiser, followedByConcept, early battleship]
-
A.
followsInConcept
chosen
Indicates that one concept comes after or is derived from another concept in a logical, thematic, or conceptual sequence.
-
B.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
C.
successorConcept
Indicates that one concept directly follows and replaces another in a sequence, versioning, or conceptual progression.
-
D.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
E.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
- 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.