Triple
T35426714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milner-Barry Gambit in the French Defence |
E1023939
|
entity |
| Predicate | ECOCode |
P182961
|
FINISHED |
| Object | C02 |
—
|
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: C02 | Statement: [Milner-Barry Gambit in the French Defence, ECOCode, C02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ECOCode Context triple: [Milner-Barry Gambit in the French Defence, ECOCode, C02]
-
A.
hasECOCode
Indicates that an entity is associated with a specific Evidence and Conclusion Ontology (ECO) code describing the type of evidence supporting it.
-
B.
codeFootprint
Indicates the extent or size of code associated with an entity, such as how much code it contains, uses, or impacts.
-
C.
eraCode
Indicates the specific historical or temporal era associated with an entity, typically encoded as a standardized era identifier.
-
D.
ecosystemIntegrationWith
Indicates how one entity is incorporated into, interacts with, or functions as part of another entity’s broader ecosystem of products, services, or systems.
-
E.
codeOn
Indicates that one entity writes, develops, or modifies software using or for another entity (such as a platform, project, or codebase).
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795933588819082ba3c1716b05d63 |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.