Triple
T11130072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isla Sorna |
E263252
|
entity |
| Predicate | primaryFunctionInFiction |
P88311
|
FINISHED |
| Object | dinosaur cloning site |
—
|
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: dinosaur cloning site | Statement: [Isla Sorna, primaryFunctionInFiction, dinosaur cloning site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFunctionInFiction Context triple: [Isla Sorna, primaryFunctionInFiction, dinosaur cloning site]
-
A.
primaryFunctionInPlot
chosen
Indicates the main narrative role or purpose that an entity serves within the plot of a story.
-
B.
workInFiction
Indicates that one entity is a fictional work in which the other entity appears or is set.
-
C.
primaryFunctionInPractice
Indicates that an entity serves as the main or most important function or role within a given practical context or real-world usage.
-
D.
fictionalUse
Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
-
E.
primaryFunctionInSeries
Indicates that an entity serves as the main or most important function within a particular series or sequence.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e831f4808190afabdaa0e97bbe32 |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.