Triple
T11881877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Mancunian |
E282676
|
entity |
| Predicate | qualifierMeaning |
P35857
|
FINISHED |
| Object | former or ex- |
—
|
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: former or ex- | Statement: [Old Mancunian, qualifierMeaning, former or ex-]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifierMeaning Context triple: [Old Mancunian, qualifierMeaning, former or ex-]
-
A.
servesAsQualifierFor
chosen
Indicates that one entity functions as a qualifier or modifier that refines, restricts, or specifies the meaning or scope of another entity.
-
B.
meaningStatus
Indicates the relationship between an entity and the status of its meaning, such as whether its meaning is defined, clear, ambiguous, or unknown.
-
C.
parameterMeaning
Indicates that one entity specifies the semantic meaning, role, or purpose of a parameter associated with another entity.
-
D.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
-
E.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.