Triple
T34087372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LBD |
E874208
|
entity |
| Predicate | typicalSilhouette |
P111728
|
FINISHED |
| Object | sheath |
—
|
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: sheath | Statement: [LBD, typicalSilhouette, sheath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSilhouette Context triple: [LBD, typicalSilhouette, sheath]
-
A.
typicalFigure
Indicates that one entity serves as a standard or representative example (a typical instance) of the other entity.
-
B.
roleInSilhouette
chosen
Indicates that an entity has a specific functional or positional role within a larger silhouette or outline structure.
-
C.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
D.
typicalHeadProfile
Indicates that an entity has a head shape or outline that conforms to a standard or commonly observed profile for its type.
-
E.
typicalStillType
Indicates that something represents the usual or characteristic form, style, or configuration that an entity typically has or uses.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.