Triple
T38447579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonefoots |
E906680
|
entity |
| Predicate | lineageTrait |
P180491
|
FINISHED |
| Object | physical sturdiness |
—
|
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: physical sturdiness | Statement: [Stonefoots, lineageTrait, physical sturdiness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineageTrait Context triple: [Stonefoots, lineageTrait, physical sturdiness]
-
A.
lineageSystem
Indicates a hierarchical ancestry or descent relationship that traces how entities are derived from or originate through one another within a system.
-
B.
basedOnCharacterLineage
Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
-
C.
hasLineageCharacteristic
chosen
Indicates that an entity possesses a specific trait, feature, or quality that is inherited or derived from its lineage or ancestral line.
-
D.
greenLineageCharacterizedBy
Indicates that a green lineage is defined or distinguished by a particular characteristic, trait, or feature.
-
E.
lineageRelatedTo
Indicates a relationship where two entities are connected through a line of descent or ancestry within the same lineage.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcce7afcd08190906cc3801152656a |
completed | May 7, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69fcccf140ec8190862d53388a5f40d7 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.