Triple
T10292948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AL MVP |
E241406
|
entity |
| Predicate | isPositionSpecific |
P13211
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [AL MVP, isPositionSpecific, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPositionSpecific Context triple: [AL MVP, isPositionSpecific, no]
-
A.
positionSpecific
chosen
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
-
B.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
-
C.
isPositionedAs
Indicates that one entity is placed or arranged in a specific spatial or conceptual position relative to another.
-
D.
isNonPositionalSince
Indicates that something has not depended on or been defined by positional context since a specified point in time.
-
E.
isSiteSpecific
Indicates that something is designed, intended, or valid only for a particular location, context, or site and does not generally apply elsewhere.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d35f048190a215493acdf1f718 |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:42 a.m.