Triple
T32894565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | little Mary |
E841432
|
entity |
| Predicate | typicalReferent |
P59207
|
FINISHED |
| Object | young girl named Mary |
—
|
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: young girl named Mary | Statement: [little Mary, typicalReferent, young girl named Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalReferent Context triple: [little Mary, typicalReferent, young girl named Mary]
-
A.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
B.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
C.
primaryReferent
chosen
Indicates that one entity is the main or most salient referent associated with another entity among potentially multiple candidates.
-
D.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
E.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:18 a.m.