Triple
T26580706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1893 Isabella quarter |
E667068
|
entity |
| Predicate | reverseText |
P1465
|
FINISHED |
| Object | BOARD OF LADY MANAGERS |
—
|
NE NERFINISHED |
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: BOARD OF LADY MANAGERS | Statement: [1893 Isabella quarter, reverseText, BOARD OF LADY MANAGERS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reverseText Context triple: [1893 Isabella quarter, reverseText, BOARD OF LADY MANAGERS]
-
A.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
-
B.
reverseInscription
chosen
Indicates that one entity is inscribed as the reverse or mirror image of another entity’s inscription.
-
C.
reverseFeature
Indicates that one feature is the inverse or opposite counterpart of another feature in a given context.
-
D.
reversesPronouncement
Indicates that one entity invalidates or overturns a prior formal statement, decision, or declaration made by another entity.
-
E.
reverseMotto
Indicates that one entity is the reverse (character-by-character or order-wise inverted) form of another entity’s motto or slogan.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:03 a.m.