Triple
T22678145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs Eaves |
E560402
|
entity |
| Predicate | availableWidth |
P149206
|
FINISHED |
| Object | narrow |
—
|
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: narrow | Statement: [Mrs Eaves, availableWidth, narrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableWidth Context triple: [Mrs Eaves, availableWidth, narrow]
-
A.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
B.
hasApproximateMaximumWidth
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
C.
hasWidth
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
D.
sectionWidthGranted
Indicates that a specific width has been allocated or approved for a section within a layout or structure.
-
E.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
- F. None of above. chosen
Provenance (4 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1785d93e48190b37d11642b0cb123 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:11 p.m.