Triple
T12348785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell Estate |
E294428
|
entity |
| Predicate | roleInKapolei |
P8234
|
FINISHED |
| Object | major master developer |
—
|
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: major master developer | Statement: [Campbell Estate, roleInKapolei, major master developer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInKapolei Context triple: [Campbell Estate, roleInKapolei, major master developer]
-
A.
roleAtSavoIsland
Indicates the specific role, position, or function an entity held in relation to the event or context associated with Savo Island.
-
B.
roleAtOkinawa
Indicates the specific role, position, or function an entity held in relation to the event or context of Okinawa.
-
C.
roleInPhilippines
Indicates that an entity holds or has held an official or notable role, position, or function within the Philippines.
-
D.
hasCityRole
chosen
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
E.
roleInAdministrativeDivision
Indicates that an entity holds or fulfills a specific role, function, or position within a particular administrative division or jurisdiction.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7ba17481908b03af7316b28d9b |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.