Triple
T10783775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Century Division |
E254397
|
entity |
| Predicate | preMerger |
P65379
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Century Division, preMerger, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preMerger Context triple: [Century Division, preMerger, true]
-
A.
hasMerger
Indicates a relationship where two or more entities combine into a single entity through a merger event.
-
B.
preIntegration
chosen
Indicates a relationship or state that exists or actions that occur before an integration process takes place.
-
C.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
D.
conferenceBeforeMerger
Indicates that a conference or meeting took place prior to a merger event between entities.
-
E.
playedBeforeMerger
Indicates that one entity participated in or engaged in play prior to a specified merger event involving the other entity.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d1b4bc8190871dd21265065705 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.