Triple
T25209418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (Bong.) Carrière |
E631640
|
entity |
| Predicate | appliesToFamily |
P1129
|
FINISHED |
| Object | Pinaceae |
—
|
NE NERFINISHED |
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: Pinaceae | Statement: [(Bong.) Carrière, appliesToFamily, Pinaceae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToFamily Context triple: [(Bong.) Carrière, appliesToFamily, Pinaceae]
-
A.
appliesToLanguageFamily
Indicates that something (such as a rule, feature, or classification) is relevant or applicable to an entire language family rather than to a single language.
-
B.
allowsForFamily
Indicates that one entity enables or makes it possible for another entity to support or include family-related participation, benefits, or involvement.
-
C.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
appliesToVariantFamily
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to an entire family or group of related variants rather than to a single specific variant.
-
E.
supportsModelFamily
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or use of a particular model family.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 12:58 p.m.