Triple
T37523288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worldwide Act |
E932836
|
entity |
| Predicate | hasRegionComponent |
P285
|
FINISHED |
| Object | Europe |
E833
|
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: Europe | Statement: [Worldwide Act, hasRegionComponent, Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionComponent Context triple: [Worldwide Act, hasRegionComponent, Europe]
-
A.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
B.
hasComponentTerritory
Indicates that one territory is a constituent or subordinate part of a larger, encompassing territory.
-
C.
hasRegionFunction
Indicates that a region is associated with a particular function, role, or operational purpose.
-
D.
hasRegionProperty
Indicates that a region is associated with a specific property or characteristic.
-
E.
hasRegionKey
Indicates that an entity is associated with a specific region through a unique identifying key.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409527a5b481908e0fc1923b46f406 |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.