Triple
T29862790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Falls |
E758366
|
entity |
| Predicate | connectedToArtifact |
P845
|
FINISHED |
| Object | The Emerald Atlas (magical book) |
—
|
NE NERFINISHED |
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: The Emerald Atlas (magical book) | Statement: [Cambridge Falls, connectedToArtifact, The Emerald Atlas (magical book)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToArtifact Context triple: [Cambridge Falls, connectedToArtifact, The Emerald Atlas (magical book)]
-
A.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
-
B.
relatedArtifactType
Indicates the specific kind of relationship or linkage that one artifact has to another artifact (e.g., predecessor, successor, reference, dependency).
-
C.
connectedToEvent
Indicates that an entity has a direct association or linkage with a specific event.
-
D.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
articulatedWith
Indicates that two parts are connected by a joint or mechanism that allows controlled movement between them.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 29, 2026, 5:50 p.m.