Triple
T18043783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manx advocates |
E431719
|
entity |
| Predicate | shareFeaturesWith |
P5696
|
FINISHED |
| Object | Scottish advocates |
—
|
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: Scottish advocates | Statement: [Manx advocates, shareFeaturesWith, Scottish advocates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareFeaturesWith Context triple: [Manx advocates, shareFeaturesWith, Scottish advocates]
-
A.
sharesFeatureWith
chosen
Indicates that two entities have at least one common attribute, property, or characteristic in common.
-
B.
shareFeature
Indicates that two or more entities possess at least one common attribute, property, or characteristic.
-
C.
shareWith
Indicates that something is given, disclosed, or made accessible by one entity to another entity.
-
D.
sharesModuleWith
Indicates that two entities are associated with or participate in at least one common module.
-
E.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff072508190a4065e3f83997aa9 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.