Triple
T28527139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linb |
E721936
|
entity |
| Predicate | scriptAgeClassification |
P110301
|
FINISHED |
| Object | ancient script |
—
|
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: ancient script | Statement: [Linb, scriptAgeClassification, ancient script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptAgeClassification Context triple: [Linb, scriptAgeClassification, ancient script]
-
A.
hasAgeClassification
chosen
Indicates that an entity is associated with a specific age-based category or grouping.
-
B.
ageSystem
Indicates a relationship where one entity specifies or uses a particular system or standard for expressing age (e.g., calendar system, counting convention, or age-measurement method) for another entity.
-
C.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
D.
ageType
Indicates the specific categorization or classification of an age value (e.g., actual, estimated, range-based) associated with an entity.
-
E.
ageStatus
Indicates the relationship between an entity and its classification into an age-related category or status (e.g., minor, adult, senior).
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 3:25 a.m.