Triple
T8756472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GraphQL |
E208081
|
entity |
| Predicate | notableScalarType |
P85213
|
FINISHED |
| Object | Int |
—
|
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: Int | Statement: [GraphQL, notableScalarType, Int]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableScalarType Context triple: [GraphQL, notableScalarType, Int]
-
A.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
B.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
C.
notableStandard
Indicates that one entity is a widely recognized or influential standard that the other entity is associated with or exemplifies.
-
D.
notableStoreType
Indicates that a store is particularly recognized or distinguished for being of a specified type (e.g., a notable example of that kind of store).
-
E.
notableSegmentType
Indicates that a particular segment or portion of something is classified as being of notable or special significance by its type.
- 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd95e9481909cc88e8d91601754 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:40 p.m.