Triple
T6550728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serunai |
E151120
|
entity |
| Predicate | hasReedType |
P71751
|
FINISHED |
| Object | double reed |
—
|
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 reed | Statement: [Serunai, hasReedType, double reed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReedType Context triple: [Serunai, hasReedType, double reed]
-
A.
hasReadingRoomType
Indicates that an entity (such as a facility or building) has a specific type or category of reading room.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasSternType
Indicates that an entity (typically a vessel) possesses a specific type or design of stern.
-
D.
sealType
Indicates the specific kind or category of seal associated with an entity or connection.
-
E.
hasReadingType
Indicates that an entity is associated with a specific category or mode of reading, such as a particular interpretation, format, or type of reading measurement.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6c1b007148190b5164d6d09584cdf |
completed | March 27, 2026, 5:43 p.m. |
Created at: March 27, 2026, 1:51 p.m.