Triple
T38278026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-A‘sha |
E1022010
|
entity |
| Predicate | metricSystem |
P29841
|
FINISHED |
| Object | classical Arabic prosody |
—
|
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: classical Arabic prosody | Statement: [Al-A‘sha, metricSystem, classical Arabic prosody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metricSystem Context triple: [Al-A‘sha, metricSystem, classical Arabic prosody]
-
A.
meterSystem
Indicates that one entity uses, is measured in, or is associated with a particular system of meters or measurement units.
-
B.
mètre
Indicates a measurement relationship where one entity serves as the unit "meter" used to quantify the length, distance, or size of another entity.
-
C.
isMetric
Indicates that something satisfies the properties required to be considered a metric, such as defining distances that obey non-negativity, identity, symmetry, and the triangle inequality.
-
D.
unitSystem
chosen
Indicates the system of measurement units (such as metric or imperial) that is used to quantify associated values or attributes.
-
E.
meter
Indicates a measurement relationship where one entity quantifies the length, distance, or extent of another in meters.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.