Triple
T38612575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pearly Queen |
E934519
|
entity |
| Predicate | inheritsRole |
P191293
|
FINISHED |
| Object | within families |
—
|
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: within families | Statement: [Pearly Queen, inheritsRole, within families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inheritsRole Context triple: [Pearly Queen, inheritsRole, within families]
-
A.
inheritsMembersFrom
Indicates that one entity receives or derives its members, properties, or characteristics from another entity.
-
B.
impliesRole
Indicates that one role logically entails or gives rise to another role within a given context or system.
-
C.
inheritsTitle
Indicates that one entity receives and assumes a formal title or rank previously held by another entity, typically through succession or inheritance.
-
D.
inheritsSymbolFrom
Indicates that one entity derives or receives its symbolic representation or notation from another entity.
-
E.
hasSubrole
Indicates that one role functions as a more specific, subordinate, or specialized version of another broader role.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.