Triple
T33265813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lotus principle |
E851641
|
entity |
| Predicate | originatedFromDisputeBetween |
P61098
|
FINISHED |
| Object | France |
E861
|
NE 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: France | Statement: [Lotus principle, originatedFromDisputeBetween, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedFromDisputeBetween Context triple: [Lotus principle, originatedFromDisputeBetween, France]
-
A.
originatingDispute
chosen
Indicates that one entity is the source, cause, or initial context of a particular dispute involving another entity.
-
B.
disputeOrigin
Indicates that there is disagreement or uncertainty about the source, cause, or initial point of something.
-
C.
hasDisputeWith
Indicates that there is a conflict, disagreement, or contested issue between two entities.
-
D.
laterDisputedBy
Indicates that a previously made claim, statement, or assertion is subsequently challenged, questioned, or contradicted by another party.
-
E.
disputeBegan
Indicates that a conflict or disagreement between parties was initiated or came into existence at a specific point in time.
- F. None of above.
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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a030425fa1c81908748583513552d2b |
completed | May 12, 2026, 10:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a35390f8d58819090d5b1d13685617a |
completed | June 19, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_6a0303ced28081908588b8a14c23efe9 |
completed | May 12, 2026, 10:41 a.m. |
Created at: May 1, 2026, 1:32 a.m.