Triple
T6895435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PM |
E159159
|
entity |
| Predicate | hasAmbiguityWith |
P31777
|
FINISHED |
| Object | post meridiem |
—
|
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: post meridiem | Statement: [PM, hasAmbiguityWith, post meridiem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAmbiguityWith Context triple: [PM, hasAmbiguityWith, post meridiem]
-
A.
isAmbiguousName
Indicates that a name can refer to multiple distinct entities or interpretations, making its reference unclear without additional context.
-
B.
languageAmbiguity
chosen
Indicates that the meaning, interpretation, or reference of a linguistic expression is unclear or can be understood in multiple ways.
-
C.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
D.
hasDisambiguationNote
Indicates that there is an explanatory note used to distinguish this entity or term from other entities or terms with similar or identical names.
-
E.
hasRelatedConflict
Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d933032c8190997d67a15897619b |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:24 p.m.