Triple
T34696735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lu (surname) |
E891050
|
entity |
| Predicate | isWrittenBeforeGivenNameIn |
P28784
|
FINISHED |
| Object | Chinese naming order |
—
|
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: Chinese naming order | Statement: [Lu (surname), isWrittenBeforeGivenNameIn, Chinese naming order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWrittenBeforeGivenNameIn Context triple: [Lu (surname), isWrittenBeforeGivenNameIn, Chinese naming order]
-
A.
hasNameOrder
chosen
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
-
B.
hasGivenNames
Indicates that an entity possesses one or more personal (given) names assigned to it.
-
C.
isGivenNameInCulture
Indicates that a particular given (first) name is used or recognized within a specified culture or cultural context.
-
D.
isGivenName
Indicates that one entity is the personal (given) name of another entity.
-
E.
nameWrittenIn
Indicates that an entity’s name is written or recorded using a specified language, script, or writing system.
- 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7238028bc81909af7928b093250ff |
completed | May 3, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.