Triple
T25320076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culler–Vogtmann Outer space |
E634851
|
entity |
| Predicate | rankParameter |
P158385
|
FINISHED |
| Object | n ≥ 2 |
—
|
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: n ≥ 2 | Statement: [Culler–Vogtmann Outer space, rankParameter, n ≥ 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankParameter Context triple: [Culler–Vogtmann Outer space, rankParameter, n ≥ 2]
-
A.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
B.
rankProperty
Indicates that one entity is assigned a position or level in an ordered scale or hierarchy based on a specified property or criterion.
-
C.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
D.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
E.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4968d6e848190bcb8668b6dc3f183 |
completed | May 1, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:28 p.m.