Triple
T3768734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tour Voile |
E82743
|
entity |
| Predicate | requiresOffshoreExperience |
P51023
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tour Voile, requiresOffshoreExperience, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresOffshoreExperience Context triple: [Tour Voile, requiresOffshoreExperience, yes]
-
A.
requiresCitizenship
Indicates that one entity can only obtain, access, or participate in another entity if it holds citizenship of a specified country or jurisdiction.
-
B.
couldServeOverseas
Indicates that an entity has the ability or eligibility to perform service or duties in a foreign or overseas location.
-
C.
locatedInOverseasCountry
Indicates that an entity is situated in a country that is overseas relative to a given reference location or jurisdiction.
-
D.
hasOverseasPresenceIn
Indicates that an entity maintains operations, offices, or activities in a foreign country or region.
-
E.
appointmentRequirement
Indicates that a particular action, service, or interaction can only occur if an appointment has been scheduled or a specified appointment condition is met.
- F. None of above. chosen
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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc2d4b848190bf63fb3ed5d3b2d9 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:35 p.m.