Triple
T5416181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maquis |
E121136
|
entity |
| Predicate | hadInternalDivision |
P63526
|
FINISHED |
| Object | communist groups |
—
|
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: communist groups | Statement: [Maquis, hadInternalDivision, communist groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadInternalDivision Context triple: [Maquis, hadInternalDivision, communist groups]
-
A.
hasCivilDivision
Indicates that one administrative or political entity is subdivided into, or is associated with, a specific civil division (such as a county, district, or municipality).
-
B.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
-
C.
hasFieldDivision
Indicates that one entity is organizationally divided into, or associated with, a specific field-based subdivision of another entity.
-
D.
historicallyDividedInto
Indicates that an entity was separated into multiple distinct parts or regions during a past historical period.
-
E.
wasDividedByTreaty
Indicates that an entity (such as a territory or region) was partitioned or separated as the result of a formal treaty or agreement.
- F. None of above. chosen
Provenance (4 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bff75881909bdfd2cdf7ff5657 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd8741e8588190863fd5cfb559136d |
completed | March 20, 2026, 5:43 p.m. |
Created at: March 20, 2026, 2:05 p.m.