Triple
T193657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Economic Conference |
E3772
|
entity |
| Predicate | hadNumberOfParticipatingCountries |
P2436
|
FINISHED |
| Object | 66 |
—
|
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: 66 | Statement: [London Economic Conference, hadNumberOfParticipatingCountries, 66]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNumberOfParticipatingCountries Context triple: [London Economic Conference, hadNumberOfParticipatingCountries, 66]
-
A.
numberOfParticipatingNations
chosen
Indicates the total count of nations that take part in a specified event, activity, or context.
-
B.
hasNumberOfCountries
Indicates the relationship that specifies how many countries are associated with or contained within a given entity.
-
C.
involvedCountry
Indicates that a country participates in, is associated with, or is otherwise implicated in the referenced event, activity, or situation.
-
D.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
E.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a2596810c48190ab687c0c2efaa9e2 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a256769ad8819083c1d83082c0215e |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.