Triple
T5385703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | motaqareb metre |
E120196
|
entity |
| Predicate | hasFootPattern |
P27772
|
FINISHED |
| Object | fa‘ulun fa‘ulun fa‘ulun fa‘ul |
—
|
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: fa‘ulun fa‘ulun fa‘ulun fa‘ul | Statement: [motaqareb metre, hasFootPattern, fa‘ulun fa‘ulun fa‘ulun fa‘ul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootPattern Context triple: [motaqareb metre, hasFootPattern, fa‘ulun fa‘ulun fa‘ulun fa‘ul]
-
A.
footType
Indicates the specific kind or classification of feet that an entity possesses or is characterized by.
-
B.
hasStandardToeCount
Indicates that an entity possesses the typical or expected number of toes for its kind.
-
C.
hasFootfallPattern
chosen
Indicates a characteristic pattern or sequence of steps, movements, or impacts made by an entity’s feet during locomotion or activity.
-
D.
hasPavementPattern
Indicates that an entity possesses or is characterized by a specific pattern or design in its pavement surface.
-
E.
hasSettlementAtFoot
Indicates that a settlement is located at the base or lower slopes of a geographic feature such as a hill or mountain.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd86f5a7388190aa4ba2052afca74e |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.