Triple
T31138945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marilyns of Northern Ireland |
E793726
|
entity |
| Predicate | sharesDefinitionWith |
P197982
|
FINISHED |
| Object | Marilyns of Scotland |
—
|
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: Marilyns of Scotland | Statement: [Marilyns of Northern Ireland, sharesDefinitionWith, Marilyns of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesDefinitionWith Context triple: [Marilyns of Northern Ireland, sharesDefinitionWith, Marilyns of Scotland]
-
A.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesBaseWith
Indicates that two entities have a common underlying base element, source, or component from which they are derived or constructed.
-
D.
shareWith
Indicates that something is given, disclosed, or made accessible by one entity to another entity.
-
E.
sharesModuleWith
Indicates that two entities are associated with or participate in at least one common module.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
| PDg | Predicate description generation | batch_69fec00e5c1c819083d174bb4bc35f29 |
completed | May 9, 2026, 5:03 a.m. |
Created at: April 29, 2026, 9:05 p.m.