Triple
T27871817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xióng shì |
E704509
|
entity |
| Predicate | hasSurnameCharacter |
P37098
|
FINISHED |
| Object | 熊 |
—
|
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: 熊 | Statement: [Xióng shì, hasSurnameCharacter, 熊]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurnameCharacter Context triple: [Xióng shì, hasSurnameCharacter, 熊]
-
A.
hasCharacterWithSurname
Indicates that an entity (such as a work or story) includes at least one character whose surname matches the specified name.
-
B.
hasSurnameType
Indicates that an entity’s surname belongs to a particular category or type (e.g., patronymic, toponymic, occupational).
-
C.
hasSurnamePattern
Indicates that an entity’s surname follows or matches a specified structural or stylistic pattern.
-
D.
hasSurnamePrefix
Indicates that one entity’s surname begins with, or is prefixed by, the string or component specified by the other entity.
-
E.
hasComponentSurname
chosen
Indicates that an entity’s full name includes a specified surname as one of its component parts.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 27, 2026, 6:25 p.m.