Triple
T11397941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese umbrella pine |
E270027
|
entity |
| Predicate | uniqueFamilyMember |
P99093
|
FINISHED |
| Object | sole living species in family Sciadopityaceae |
—
|
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: sole living species in family Sciadopityaceae | Statement: [Japanese umbrella pine, uniqueFamilyMember, sole living species in family Sciadopityaceae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniqueFamilyMember Context triple: [Japanese umbrella pine, uniqueFamilyMember, sole living species in family Sciadopityaceae]
-
A.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
B.
hasHouseholdMember
Indicates that one entity is a member of the same household as another entity.
-
C.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
identifiedAsFamilyIn
Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d80019d3d48190a2f473deb6eae33a |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.