Triple
T27573684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warsaw Pact advisers |
E696099
|
entity |
| Predicate | wereActiveFrom |
P7730
|
FINISHED |
| Object | 1955 |
—
|
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: 1955 | Statement: [Warsaw Pact advisers, wereActiveFrom, 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereActiveFrom Context triple: [Warsaw Pact advisers, wereActiveFrom, 1955]
-
A.
activeFrom
chosen
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
B.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
C.
activeInBandSince
Indicates that an entity has been an active member of a band starting from a specified point in time.
-
D.
historicallyActiveIn
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
-
E.
activatedAs
Indicates that one entity has been put into an active or operational state in the role or capacity of another specified 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62fee64148190b84b7a1b6e9cccbe |
completed | May 2, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:44 p.m.