Triple
T4418003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mc |
E95023
|
entity |
| Predicate | usedToIndicate |
P37164
|
FINISHED |
| Object | paternal lineage |
—
|
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: paternal lineage | Statement: [Mc, usedToIndicate, paternal lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToIndicate Context triple: [Mc, usedToIndicate, paternal lineage]
-
A.
usesIndicator
Indicates that one entity employs or relies on another entity as an indicator, signal, or metric for assessment, decision-making, or interpretation.
-
B.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
-
C.
canAlsoIndicate
chosen
Indicates that something may additionally signify, represent, or serve as another meaning or function beyond its primary one.
-
D.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
E.
isUsedToIllustrate
Indicates that one entity serves as an example or demonstration to clarify, explain, or represent another entity.
- 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.