Triple
T480776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PHP |
E9160
|
entity |
| Predicate | hasSymbolPlacement |
P2875
|
FINISHED |
| Object | before amount in common usage |
—
|
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: before amount in common usage | Statement: [PHP, hasSymbolPlacement, before amount in common usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSymbolPlacement Context triple: [PHP, hasSymbolPlacement, before amount in common usage]
-
A.
hasCurrencySignPlacement
chosen
Indicates where the currency sign is positioned relative to the numeric amount in a monetary value.
-
B.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
C.
hasPlantSymbol
Indicates that an entity is associated with or represented by a particular plant as its symbolic emblem or sign.
-
D.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
E.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f058ebe48190aaa0a829b21f75fa |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.