Triple
T38461139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Thousand Footer Committee |
E912455
|
entity |
| Predicate | usesListType |
P5109
|
FINISHED |
| Object | summit list based on elevation threshold |
—
|
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: summit list based on elevation threshold | Statement: [Four Thousand Footer Committee, usesListType, summit list based on elevation threshold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesListType Context triple: [Four Thousand Footer Committee, usesListType, summit list based on elevation threshold]
-
A.
usesList
Indicates that one entity employs or relies on another entity in the form of a list or ordered collection.
-
B.
listType
chosen
Indicates that one entity specifies the classification or category type of a list associated with another entity.
-
C.
listAPurpose
Indicates that an entity enumerates or specifies the purposes, goals, or intended uses associated with another entity.
-
D.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
E.
usesEnum
Indicates that one entity employs or references an enumeration type defined by 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_69f76e861d8c81908559031dc66e3c15 |
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.