Triple
T29649391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rehe region |
E756091
|
entity |
| Predicate | timePeriodOfMajorContestation |
P28865
|
FINISHED |
| Object | early 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: early 20th century | Statement: [Rehe region, timePeriodOfMajorContestation, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfMajorContestation Context triple: [Rehe region, timePeriodOfMajorContestation, early 20th century]
-
A.
timeOfMajorDebate
Indicates the specific time at which a major debate takes place or is scheduled.
-
B.
timePeriodOfMajorMilitaryActivity
Indicates the time span during which the primary or most significant military operations associated with an entity took place.
-
C.
conflictPeriod
chosen
Indicates the time span during which a particular conflict or dispute is occurring or in effect between the related entities.
-
D.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
-
E.
timePeriodOfMajorDispossession
Indicates the time span during which the primary or most significant act of dispossession occurred.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 6:51 p.m.