Triple
T1456576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French East India Company |
E31413
|
entity |
| Predicate | hadMilitaryRole |
P22805
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [French East India Company, hadMilitaryRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMilitaryRole Context triple: [French East India Company, hadMilitaryRole, yes]
-
A.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
hasMilitaryBranch
Indicates that an entity is associated with, served in, or is part of a specific branch of a military organization.
-
C.
hasMilitaryAssociation
chosen
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
-
D.
hasMilitaryServiceStart
Indicates the date or point in time when an entity’s period of military service began.
-
E.
militaryStatus
Indicates the relationship between an entity and a military organization in terms of service condition, such as active duty, reserve, veteran, or non-military status.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c598b30c8190b87207adf608b89a |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.