Triple
T10090242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conseil |
E215322
|
entity |
| Predicate | relationshipWithNedLand |
P92381
|
FINISHED |
| Object | friend |
—
|
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: friend | Statement: [Conseil, relationshipWithNedLand, friend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithNedLand Context triple: [Conseil, relationshipWithNedLand, friend]
-
A.
logisticsSupportFrom
Indicates that one entity provides logistical assistance, resources, or services to another entity.
-
B.
associatedWithAnimal
Indicates a relationship where an entity has a connection, link, or relevance to an animal.
-
C.
associatedWithSea
Indicates a relationship in which something has a connection, relevance, or linkage to the sea or marine environment.
-
D.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
E.
domesticationCenter
Indicates the place or region where a species was first brought under human control and selectively bred, marking the origin of its domestication.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd05960008190baecb8e4c9f2461f |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd5150ae98819086c4f822114b4e2c |
completed | April 1, 2026, 5:09 p.m. |
Created at: March 30, 2026, 9:01 p.m.