Triple
T26966707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RP |
E679190
|
entity |
| Predicate | relationToP |
P34778
|
FINISHED |
| Object | P is a subset of RP |
—
|
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: P is a subset of RP | Statement: [RP, relationToP, P is a subset of RP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToP Context triple: [RP, relationToP, P is a subset of RP]
-
A.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
B.
termRelationTo
chosen
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
C.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
-
D.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
-
E.
relationToOTO
Indicates a relationship in which one entity stands in a specified connection or association to an "OTO" entity (such as being linked, related, or corresponding to it).
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: April 27, 2026, 6:36 a.m.