Triple
T3349339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mette-Sophie Gad |
E70450
|
entity |
| Predicate | spouseTravelPurpose |
P47388
|
FINISHED |
| Object | to pursue art in Tahiti |
—
|
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: to pursue art in Tahiti | Statement: [Mette-Sophie Gad, spouseTravelPurpose, to pursue art in Tahiti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseTravelPurpose Context triple: [Mette-Sophie Gad, spouseTravelPurpose, to pursue art in Tahiti]
-
A.
typicalJourneyPurpose
Indicates the usual or most common reason or objective for which an entity undertakes a journey.
-
B.
spouseMovement
Indicates a movement or relocation event involving a person and their spouse, such as moving together or one moving to join the other.
-
C.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, partner).
-
D.
sunJourneyPurpose
Indicates the purpose or intended goal behind a sun-related journey or movement.
-
E.
spouse
Indicates that two entities are married to each other in a legally or socially recognized partnership.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb21f3ae48190a33530712da01bc3 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.