Triple
T27711483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British people |
E698702
|
entity |
| Predicate | sharesCommonIdentityWith |
P40775
|
FINISHED |
| Object | English people |
—
|
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: English people | Statement: [British people, sharesCommonIdentityWith, English people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesCommonIdentityWith Context triple: [British people, sharesCommonIdentityWith, English people]
-
A.
sharesIdentityWith
Indicates that two entities are considered to have the same identity, referring to the very same underlying individual or object rather than merely being similar or related.
-
B.
sharesElementsWith
chosen
Indicates that two entities have one or more elements or components in common.
-
C.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
-
D.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 27, 2026, 3:02 p.m.