Triple
T21226670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NRF |
E523100
|
entity |
| Predicate | supportsSelection |
P107474
|
FINISHED |
| Object | load-based NF selection |
—
|
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: load-based NF selection | Statement: [NRF, supportsSelection, load-based NF selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSelection Context triple: [NRF, supportsSelection, load-based NF selection]
-
A.
supportsItemSelection
chosen
Indicates that an entity provides functionality for choosing one or more items from a set.
-
B.
holderSelection
Indicates that a particular entity has been chosen or designated to serve as the holder of another entity or resource.
-
C.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
D.
supportsColumnSelectionBy
Indicates that one entity enables or provides functionality for another entity to select specific columns.
-
E.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734ab3f6c819083e277ea1c33134e |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.