Triple
T25099391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion, Bataan |
E628680
|
entity |
| Predicate | hasRegionalGrouping |
P5147
|
FINISHED |
| Object | Luzon island group |
—
|
NE NERFINISHED |
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: Luzon island group | Statement: [Orion, Bataan, hasRegionalGrouping, Luzon island group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalGrouping Context triple: [Orion, Bataan, hasRegionalGrouping, Luzon island group]
-
A.
regionalGrouping
chosen
Indicates that entities are organized or associated together based on shared geographic or regional characteristics.
-
B.
vernacularGrouping
Indicates a relationship where entities are grouped together based on a shared vernacular, such as common local language, dialect, or colloquial naming.
-
C.
hasGlobalRegion
Indicates that an entity is associated with or belongs to a specific global geographic region.
-
D.
hasRegionalIdentity
Indicates that an entity possesses or is associated with a specific regional or local identity.
-
E.
hasRegionalProfile
Indicates that an entity is associated with or characterized by a specific regional profile or set of region-based attributes.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 18, 2026, 6:25 a.m.