Triple
T17568712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PassthroughSubject |
E427881
|
entity |
| Predicate | genericOver |
P36369
|
FINISHED |
| Object | Output |
—
|
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: Output | Statement: [PassthroughSubject, genericOver, Output]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genericOver Context triple: [PassthroughSubject, genericOver, Output]
-
A.
generalizationTo
Indicates that one concept or entity is a more general, abstract, or encompassing version of another, capturing a broader category or superset relationship.
-
B.
generalizationOf
Indicates that one entity represents a broader, more general concept or category that subsumes or abstracts over another, more specific entity.
-
C.
generalizedForm
Indicates that one entity is a more abstract, generalized version or broader form of another entity.
-
D.
givenFor
Indicates that something is provided, offered, or assigned in favor of or on behalf of a particular entity or purpose.
-
E.
appliesOver
chosen
Indicates that one entity’s effect, rule, or condition extends across or is valid for a specified range, domain, or set of entities.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592f29d08190bc3de905d35af849 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.