Triple
T36411614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act II of Much Ado About Nothing |
E896893
|
entity |
| Predicate | structurePosition |
P137180
|
FINISHED |
| Object | early act |
—
|
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: early act | Statement: [Act II of Much Ado About Nothing, structurePosition, early act]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structurePosition Context triple: [Act II of Much Ado About Nothing, structurePosition, early act]
-
A.
positionStructure
chosen
Indicates a spatial or organizational arrangement relationship, specifying how one structure is positioned or configured relative to another.
-
B.
classPosition
Indicates the relative ordering or rank of an entity within a class, group, or sequence.
-
C.
componentPosition
Indicates the spatial or logical placement of a component relative to a larger structure or system.
-
D.
structureFunction
Indicates that one entity’s physical or organizational structure serves a particular function or role in relation to another entity.
-
E.
subjectPosition
Indicates the spatial or logical position of a subject relative to a reference frame, context, or other entities.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.