Triple
T4418001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mc |
E95023
|
entity |
| Predicate | denotesRelationship |
P12753
|
FINISHED |
| Object | filial relationship |
—
|
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: filial relationship | Statement: [Mc, denotesRelationship, filial relationship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesRelationship Context triple: [Mc, denotesRelationship, filial relationship]
-
A.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
B.
definesRelationshipBetween
Indicates that one entity specifies or establishes the nature, type, or rules of a relationship that exists between two or more other entities.
-
C.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
D.
portraysRelationship
Indicates that one entity depicts, represents, or illustrates a relationship between other entities.
-
E.
semanticRelation
chosen
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3551d5d7481908528c2de0a6fda06 |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5d0c54819085c08533bb58030a |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:29 p.m.