Triple
T32775514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navini Island |
E838190
|
entity |
| Predicate | targetVisitorProfile |
P43376
|
FINISHED |
| Object | honeymooners |
—
|
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: honeymooners | Statement: [Navini Island, targetVisitorProfile, honeymooners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetVisitorProfile Context triple: [Navini Island, targetVisitorProfile, honeymooners]
-
A.
visitorProfile
chosen
Indicates a relationship where a profile encapsulates information or attributes associated with a particular visitor.
-
B.
targetMemberProfile
Indicates that one entity is the specific member profile that is the focus or destination of another entity’s action or reference.
-
C.
participantProfile
Indicates that an entity serves as the profile or descriptive record associated with a particular participant in an event, activity, or process.
-
D.
hasTouristProfile
Indicates that an entity possesses characteristics, data, or attributes defining it as a tourist or related to tourism behavior.
-
E.
typicalVisitorOrigin
Indicates the usual geographic source or location from which visitors to a place, event, or entity most commonly come.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 1, 2026, 1:13 a.m.