Triple
T4968294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faetar |
E111579
|
entity |
| Predicate | preservesFeatureType |
P17760
|
FINISHED |
| Object | archaic Romance features |
—
|
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: archaic Romance features | Statement: [Faetar, preservesFeatureType, archaic Romance features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservesFeatureType Context triple: [Faetar, preservesFeatureType, archaic Romance features]
-
A.
preservesFeature
chosen
Indicates that one entity maintains or keeps intact a particular feature, property, or characteristic of another entity during some process or interaction.
-
B.
protectsFeature
Indicates that one entity safeguards, preserves, or defends a particular feature or characteristic of another entity.
-
C.
preservationType
Indicates the method or process by which something is preserved or kept from deterioration.
-
D.
preservesFragmentsOf
Indicates that one entity maintains, protects, or keeps intact partial remains or pieces of another entity.
-
E.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd72e49b048190bac55d9e7a6f7963 |
completed | March 20, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69bd71447fe88190bb62c5e8753da7a7 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:32 p.m.