Triple
T28711740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabic Presentation Forms-A |
E729847
|
entity |
| Predicate | hasShapingType |
P175653
|
FINISHED |
| Object | initial forms |
—
|
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: initial forms | Statement: [Arabic Presentation Forms-A, hasShapingType, initial forms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShapingType Context triple: [Arabic Presentation Forms-A, hasShapingType, initial forms]
-
A.
hasTerminalShape
Indicates that one entity possesses or exhibits a particular terminal (end) shape defined by another entity.
-
B.
hasShapeModel
Indicates that an entity is associated with a specific geometric or structural shape model that represents its form.
-
C.
hasArchShape
Indicates that something possesses or exhibits an arched or curved shape.
-
D.
hasSectionShape
Indicates that one entity possesses or is characterized by a particular cross-sectional shape specified by another entity.
-
E.
hasPieceShape
Indicates that one entity has, exhibits, or is characterized by a particular shape or geometric form.
- F. None of above. chosen
Provenance (4 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 28, 2026, 5:48 a.m.