Triple
T3655418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Temple, Amritsar |
E77516
|
entity |
| Predicate | langarCharacteristic |
P662
|
FINISHED |
| Object | free community kitchen |
—
|
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: free community kitchen | Statement: [Golden Temple, Amritsar, langarCharacteristic, free community kitchen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: langarCharacteristic Context triple: [Golden Temple, Amritsar, langarCharacteristic, free community kitchen]
-
A.
logisticalCharacteristic
Indicates the logistical properties or constraints associated with an entity, such as how it is stored, transported, handled, or supplied.
-
B.
legCharacteristic
Indicates a characteristic, property, or attribute that specifically pertains to the legs of an entity.
-
C.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
D.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
E.
usesLineCharacteristic
Indicates that one entity employs or is based on a specific characteristic or property of a line.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3baf57c8190b72b5d1b910d9db6 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.