Triple
T27678534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coastal Renaissance |
E697844
|
entity |
| Predicate | hasBow |
P179913
|
FINISHED |
| Object | double-ended |
—
|
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: double-ended | Statement: [Coastal Renaissance, hasBow, double-ended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBow Context triple: [Coastal Renaissance, hasBow, double-ended]
-
A.
hasBowType
Indicates that an entity possesses or is associated with a specific type or category of bow.
-
B.
hasBowColor
Indicates that one entity possesses or is associated with a bow whose color is specified by another entity.
-
C.
hasBowHairMaterial
Indicates that an entity’s hair bow is made from a specified material.
-
D.
hasBore
Indicates that one object possesses or is characterized by a specific bore, such as the internal diameter of a tube, pipe, or barrel.
-
E.
hasBroad
Indicates that one entity possesses or exhibits a wide or extensive scope, range, or coverage in relation to another entity or 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 27, 2026, 2:45 p.m.